-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Full Changesets usage to automate releases #174
Conversation
|
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #174 +/- ##
=======================================
Coverage 92.52% 92.52%
=======================================
Files 37 37
Lines 3011 3011
Branches 326 326
=======================================
Hits 2786 2786
Misses 225 225
|
TBDocs Report 🛑 Errors: 0 @tbdex/protocol
@tbdex/http-client
@tbdex/http-server
TBDocs Report Updated at 2024-02-21T16:54:38Z |
|
||
When a changeset PR is merged to main we will automatically create a GitHub release using the workflow [Create GH Release](./.github/workflows/create-gh-release.yml). | ||
Just merge the [Version Packages PR](https://github.com/TBD54566975/tbdex-js/pulls?q=is%3Apr+author%3Aapp%2Fgithub-actions+%22Version+Packages%22+) when you are ready to publish the new versions! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice, this language is much better!
NPM_TOKEN: ${{ secrets.NPM_TOKEN }} | ||
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} | ||
|
||
- name: Publish `next` preview |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so what does this do exactly? it publishes a package with version equal to next
?
what is this checking for (line below) steps.changesets.outputs.pullRequestNumber != ''
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oops, didn't read the full description, my bad
"Also, if there are any present changesets on main we are automatically publishing a preview release using the next tag."
excellent!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Leaving this unresolved for awareness!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
very cool!
one comment about dev dependencies, but lgtm! ✅
fb5d407
to
1c69cca
Compare
Completes the release pipeline which fully uses Changesets to publish to NPM, create git tags and releases with proper changelog notes.
Working evidences in a forked repo:
I've also updated the README release section.
Also, if there are any present changesets on
main
we are automatically publishing a preview release using thenext
tag.